-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Subaru: driver torque sensor Nm scaling factor and unit #1198
base: master
Are you sure you want to change the base?
Conversation
Thanks for contributing to opendbc! In order for us to review your PR as quickly as possible, check the following:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's good to have known correct units for the driver input torque signal. However:
- You switched to a new signal; it's very important to reference the same signal in Panda safety
- Having re-scaled the signal, you also need to re-scale the driver input threshold in openpilot
- You will need corresponding scaling and driver input threshold updates to Panda
In short, this is the beginning of a valid change but needs additional work, including a companion Panda PR.
Thanks for the comments, I will set up panda safety PR |
I added the scaling factor and panda PR is at commaai/panda#2016 |
This PR adds Nm unit for Subaru driver torque sensor signal for gen1 and gen2 and updates carstate to use new signal. Matched with SSM4 signal output by to jnewb1 at martinl/openpilot#80